Automated tracking of vehicle operation and synchronized media delivery

ABSTRACT

The described methods and systems decrease instances of distracted driving, encourage more frequent use of vehicle tracking services, and generally improve the risk profile of a driver and vehicle. These benefits are achieved by way of a vehicle computer system that incentivizes users to place mobile devices in a do-not-disturb (DND) mode and to activate vehicle tracking services. The vehicle computer system encourages these behaviors by enabling content delivery for devices within the vehicle based on the status of the mobile device(s) and the status of the vehicle tracking service(s).

TECHNICAL FIELD

The present disclosure generally relates to monitoring an automatedvehicle tracking service and a mobile device within a vehicle, and, moreparticularly, to synchronizing a media delivery service for devices inthe vehicle with statuses of the vehicle tracking service and the mobiledevice.

BACKGROUND

Computers are increasingly integrated in vehicles and vehicle operation,and these computers grow more powerful and capable every year. Forexample, autonomous vehicles heavily rely on computer and sensor systemsto control vehicle operation. Vehicle computers often collect data fromvarious vehicle sensors, such as global positioning systems,speedometers, odometers, and body controllers. Further, vehiclecomputers are increasingly capable of integrating with other computersystems, giving users a connected and “intelligent” computingenvironment within the vehicle cabin. Many newer vehicles especiallyrely on vehicle computers and sensor systems—particularly vehiclesautonomous driving, semi-autonomous driving, and other “intelligent”technology packages. While these vehicle computer systems enable moreand better safety features over time, mobile devices simultaneouslyfacilitate dangerous and distracted driving, such as internet browsingwhile driving, texting while driving, emailing while driving, and use ofsocial media while driving.

SUMMARY

The described methods and systems decrease instances of distracteddriving, encourage more frequent use of vehicle tracking services, andgenerally improve the risk profile of a driver and vehicle. Thesebenefits are achieved by way of a vehicle computer system thatincentivizes users to place mobile devices in a do-not-disturb DND modeand to activate vehicle tracking services. The vehicle computer systemincentivizes these behaviors by enabling content delivery based on thestatus of the mobile device(s) and the status of the vehicle trackingservice(s).

For example, in an embodiment, a vehicle computer system synchronizes acontent delivery service (e.g., for providing content via a devicewithin the vehicle) with: (i) a status or state of a DND mode of amobile device associated with a driver of the vehicle, and (ii) a statusor state of a vehicle tracking service for tracking the vehicle. Forexample, the vehicle computer system may stream or otherwise enable thedelivery of media (e.g., audio such as podcasts, music, audiobooks,etc.) or a gamified user interface to the mobile device or to anothercomputer in the vehicle when the vehicle computer system detects thatboth of the following conditions exist: (i) the mobile device is in aDND mode and (ii) the vehicle tracking service is active.

In an embodiment, if either the DND mode or the vehicle tracking serviceis not active, the vehicle computer system may halt the contentdelivery, thus encouraging users to activate (and keep activated) thevehicle tracking service and to keep their mobile devices (e.g., phones)in a DND mode.

Advantageously, when the mobile device is in a DND mode, the mobiledevice softens or deactivates alarms and notifications it mightotherwise fully output (e.g., display or sound). Accordingly, the mobiledevice is less likely to distract the driver via notifications when in aDND mode. Further, when the driver is not distracted by notifications,the driver is less likely to be lured into a potentially dangerousfollow-on activity distinct from the notification itself (e.g.,responding to a text message notification by typing a text messageresponse while driving).

Note, this summary has been provided to introduce a selection ofconcepts further described below in the detailed description. Asexplained in the detailed description, certain embodiments may includefeatures and advantages not described in this summary, and certainembodiments may omit one or more features or advantages described inthis summary.

BRIEF DESCRIPTION OF THE DRAWINGS

Each of the figures described below depicts one or more aspects of thedisclosed system(s) or method(s), according to an embodiment. Thedetailed description refers to reference numerals included in thefollowing figures.

FIG. 1 is a block diagram of the example vehicle computer system forincentivizing safe vehicle operation and tracking of vehicle operationaccording to an embodiment.

FIG. 2A depicts an example vehicle computer system for an automobileaccording to an embodiment.

FIG. 2B depicts an example vehicle computer system for an motorcycleaccording to an embodiment.

FIG. 2C depicts an example vehicle computer system for a watercraftaccording to an embodiment.

FIG. 2D depicts an example vehicle computer system for a commercialautomobile according to an embodiment.

FIG. 2E depicts an example vehicle computer system for a personalwatercraft according to an embodiment.

FIG. 2F depicts an example vehicle computer system for an aircraftaccording to an embodiment.

FIG. 2G depicts an example vehicle computer system for a recreationalvehicle according to an embodiment.

FIG. 2H depicts an example vehicle computer system for a train accordingto an embodiment.

FIG. 2I depicts an example vehicle computer system for a four-wheeleraccording to an embodiment.

FIG. 3 depicts a set of example display devices according to variousembodiments.

FIG. 4 illustrates an example method for incentivizing vehicle trackingand safe vehicle operation according to an embodiment.

DETAILED DESCRIPTION

Various techniques, systems, and methods are discussed below withreference to FIGS. 1-4. FIGS. 1-3 depict example systems and systemcomponents according to one or more embodiments, and FIG. 4 depicts amethod that may be implemented via one or more of the systems shown inFIGS. 1-4.

Specifically, the following is described: (I) an example vehiclecomputer system 100 (shown in FIG. 1), configured to incentivize safevehicle operation and tracking of vehicle operation for a vehicle 103,including an in-vehicle computer system 104 that includes a mobiledevice 105 (e.g., of a driver) and that is coupled to an externalnetwork 199; (II) example vehicles 200 (shown in FIGS. 2A-2I) that maybe utilized in the system 100 in place of or in addition to the vehicle103; (III) example displays 300 that may be utilized by the system 100to display content delivered to one or more devices within the vehicle103 or one of the vehicles 200; (IV) an example method 500 that may beimplemented by the system 100; (V) additional considerations; and (VI)general terms and phrases.

In an embodiment, the system 100 syncs content delivery for one or moredevices in the in-vehicle system 104 with the status of a DND mode ofthe mobile device 105 and a status of a vehicle tracking service fortracking the vehicle 103. For example, the system 100 may stream media(e.g., audio such as podcasts, music, audiobooks, etc.) to the mobiledevice 105 or another computer in the in-vehicle computer system 104when it detects that the mobile device 105 is in DND mode and that thevehicle tracking service is active. If either the DND mode or thevehicle tracking service is de-activated, the system 100 may haltcontent delivery, thus encouraging users to activate the vehicletracking service and to keep their mobile devices (e.g., phones) in DNDmode. Advantageously, when the mobile device 105 is in DND, the mobiledevice 105 softens or deactivates alarms and notifications it mightotherwise activate. Accordingly, the mobile device 105 is less likely todirectly distract the driver via notifications. Further, when the driveris not distracted by notifications, the driver is less likely to belured into a potentially dangerous follow-on activity (e.g., respondingto a text message notification by typing a text message response whiledriving).

I. Example Vehicle Computer System 100

FIG. 1 is a block diagram of the example system 100 for incentivizingsafe vehicle operation and tracking of vehicle operation according to anembodiment. The system 100 may include any one or more of: a network199, the vehicle 103 (which may be coupled to the network 199), a server155 that may be coupled to the network 199, and a content deliverysystem 175 that may be coupled to the network 199. The vehicle 103 mayinclude the in-vehicle computer system 104, which may include the mobiledevice 105, an on-board computer 125, or a vehicle monitor 145.

A. Example Operation of the System 100

In an embodiment, the system 100 is configured to detect a user when heor she is in or near the vehicle 103. When the user is detected, thesystem 100 monitors a set of conditions and relies on those conditionsto automatically initiate and stop content delivery to one or moredevices in the vehicle 103. Specifically, the system 100 may rely on theconditions to automatically synchronize content delivery with a statusof one or more mobile devices in the vehicle 103, a status of a vehicletracking service, or both statuses.

As an example, the system 100 may monitor a first condition indicatingwhether or not the mobile device 105 is in a DND mode or a secondcondition indicating whether or not a vehicle tracking service fortracking the vehicle 103 is active (e.g., the service may be implementedvia the vehicle monitor 145, and may be implemented for the purpose ofanalyzing risk associated with the driver or vehicle). These first andsecond conditions may be monitored by the server 155, which maycoordinate with the CDS 175 to activate and deactivate content deliveryfrom the CDS 175 to the in-vehicle computer system 104 based on theconditions tracked by the server 155.

The DND mode may be any suitable mode in which notifications of themobile device 105 are muted, softened, or disabled. In some instances,the DND mode is an explicit mode (e.g., the mobile device 105 may have amode explicitly labeled “do-not-disturb” mode). In other instances,references herein to “DND mode” refer to a state of operation for thevehicle in which one or more conditions exists. Generally speaking,these one or more conditions include: deactivated, silenced, or softenednotifications; deactivated cellular or data connections that precludeone or more incoming messages from external devices via saidconnections; a sleep or hibernation state in which the phone isapparently asleep and thus not receiving communications or otherwise notproviding normal notifications; a powered down state; etc.

For example, the DND mode may be an airplane mode that prevents themobile device 105 from receiving calls or data (e.g., emails, textmessages, etc.) from external devices. In an embodiment, the DND modemay be a state in which the volume of notifications is turned down to aquieter level or turned off completely. In the DND mode, vibrationnotifications may be left on if desired. In an embodiment, notificationvibrations are disabled in DND mode. In an embodiment, in the DND mode,the mobile device 105 may continue to receive calls (e.g., which thedriver may answer via a “speaker phone mode” provided by the mobiledevice 105 or the OBC 125). In an embodiment, the DND mode, the mobiledevice 105 does not receive calls or does not notify the driver ofincoming calls.

In any event, in some instances, the system 100 automatically places themobile device 105 in DND mode when the vehicle monitor 145 is activated.The vehicle monitor 145 may be automatically activated (e.g., when thevehicle 103 starts or when the vehicle 103 starts moving) or manually(e.g., a user may manually activate the monitor 145. In some instances,an input component (e.g., comprising software, hardware, or somecombination thereof) may initiate both the DND mode and tracking ofvehicle operation. For example, the mobile device 105 may include an appor widget that activates either or both the DND mode and the vehicletracking service.

In any event, when the mobile device 105 is in DND mode and the vehiclemonitor 145 is active, the system 100 may automatically trigger contentdelivery to the in-vehicle computer system 104 (e.g., originating fromthe CDS 175, which may be disposed external to the vehicle 103 orinternal to the vehicle 103, depending on the embodiment). The system100 may display or otherwise output the content via an output componentsuch as a speaker or display of the in-vehicle system 104. The contentmay include any one or more of: audio (e.g., music, podcasts, or audiobooks from a streaming service), video, images, games, augmented-reality(AR) graphics (e.g., superimposed on a windshield as part of a heads-updisplay), or a map.

If the mobile device 105 ceases operating in DND mode or if the vehiclemonitor 145 stops tracking and reporting vehicle operation, the system100 may automatically stop content delivery from the CDS 175.Accordingly, users of the vehicle 103 are incentivized to both keep thevehicle monitor 145 active (thus enabling tracking and analysis ofdriver or vehicle behavior) and to keep the mobile device 105 in DNDmode (thus improving the safety profile of the driver by mitigatingpotential distractions from the mobile device 105, such as alarms, phonecalls, text messages, etc.).

In an embodiment, the system 100 may control operation of the vehicle103 based on the status of vehicle tracking service. For example,vehicle tracking data may be analyzed to determine a driver is asleep orotherwise incapacitated, and the system 100 may respond by bringing thevehicle 103 to a stop. In an embodiment, autonomous operation of thevehicle 103 may be tied to the status of the vehicle tracking service.For example, in an embodiment, the vehicle 103 may only activateautonomous or semi-autonomous driving when the vehicle tracking serviceis active. Examples of semi-autonomous driving include adaptive cruisecontrol, lane detection and steering correction, automatic parallelparking, etc.

B. Example Components of the System 100

The network 199 may be any suitable network and may include one or morenodes, links, or subnetworks (e.g., personal area networks, local areanetworks, wide area networks). The network 199 may include wireless orwired links or subnetworks. The network 199 may be a proprietarynetwork, a secure public internet, a virtual private network or someother type of network, such as dedicated access lines, plain ordinarytelephone lines, satellite links, combinations of these, etc.

The vehicle 103 may be any suitable vehicle (e.g., an automobile, amotorcycle, an engineering or heavy-duty vehicle such as a tractor orsteamroller, etc.). The vehicle 103 may include an in-vehicle computersystem 104, which may include an in-vehicle network 101. Like thenetwork 199, the network 101 may be any suitable network and may includeone or more nodes, links, or subnetworks (e.g., personal area networks,local area networks, wide area networks). The network 101 may includewireless or wired links or subnetworks. The in-vehicle system 104 mayinclude a mobile device 105, an on-board computer 125, or a vehiclemonitor device 145, any one of which may be coupled to the network 101.

In some embodiments, any one or more of the systems 105, 125, 145, 155,and 175 may communicate with any other of the systems 105-175 (or withany other suitable device or system not shown) via messages conformingto any suitable communication protocol (examples of which are describedin the “Additional Considerations” section). When the network 199includes the Internet, data communications may take place over thenetwork 199 via one or more protocols from the Internet Protocol suite(e.g., TCP/IP). Thus, messaging between the server 155 and any one ormore of the mobile device 105, the OBC 125, or the vehicle monitor 145may conform with any one or more of these Internet Protocol suiteprotocols.

1. The Mobile Device 105

Generally speaking, the mobile device 105 is a portable computer systemassociated with a user (e.g., a driver or passenger of the vehicle 103),such as a tablet, a mobile phone, a laptop, or a wearable device (e.g.,a smart watch, smart glasses, etc.). The mobile device 105 may include acontroller 107 (e.g., including a memory 107 and a processor 111), acommunication interface 113, and a set of UI components 115 including anelectronic display device 119 and one or more touch sensors 117 (e.g.,integrated into the display device 119). The display device 119 may beany suitable display and may include a screen, a projector, a heads-upinterface, etc. The mobile device 105 may include additional oralternative UI components 115, including various input components 117(e.g., electro-mechanical buttons or keys, a mouse, audio sensors ormicrophones, image sensors, motion sensors, etc.) or one or more outputcomponents 119 (e.g., an audio output such as a speaker, a motiongenerating component such as haptic motor for haptic feedback, etc.).

The memory 109 may include (i) a set of instructions 110 that, whenimplemented by the processor 111, cause the processor 111 to perform oneor more operations describe herein with respect to the mobile device105, and (ii) data 112 (e.g., including input data on which theprocessor 111 may operate or output data generated by the processor111).

In example operation, the mobile device 105 enables functionalitytypically associated with tablets or mobile phones, such as webbrowsing, emailing, texting, data messaging, social media use, phonecalling, etc.

2. The OBC 125

The on-board computer (OBC) 125 is a computer system disposed withinand, if desired, integrated into, one or more components of the vehicle103 (e.g., including a display on a dash of the vehicle). The OBC 125may be permanently or temporarily installed in the vehicle 103.

The OBC 125 may include a controller 127 (e.g., including a memory 127and a processor 131), a communication interface 133, and a set of UIcomponents 135 including an electronic display device 139 and one ormore touch sensors 137 (e.g., integrated into the display device 139).The display device 139 may be any suitable display and may include ascreen, a projector, a heads-up interface, etc. In an embodiment, thedisplay 139 is integrated into a dash, console, or seat of the vehicle103. The display 139 may include a screen facing one or more of theseats of the vehicle or may including a projector to project images ontoa windshield or other surface visible to the driver or passengers (e.g.,a projection surface near the top or near the bottom of the windshield).As another example, the display 139 may not be integrated into the dashor other components of the vehicle 103. For example, the display 139 maybe temporarily mounted or installed to a vent, windshield, or some othercomponent of the vehicle 103.

In any event, the OBC 125 may include additional or alternative UIcomponents 135, including various input components 147 (e.g.,electro-mechanical buttons or keys, a mouse, audio sensors ormicrophones, image sensors, motion sensors, etc.) or one or more outputcomponents 149 (e.g., an audio output such as a speaker, a motiongenerating component such as haptic motor for haptic feedback, etc.).

The memory 129 may include (i) a set of instructions 130 that, whenimplemented by the processor 131, cause the processor 131 to perform oneor more operations described herein with respect to the OBC 125, or (ii)data 132 (e.g., including input data on which the processor 131 mayoperate or output data generated by the processor 131).

In an embodiment, the OBC 125 includes or is otherwise communicativelycoupled to a sensor system (not shown) that is installed or otherwisedisposed in the vehicle 103 (e.g., via a wired or wireless link). Forexample, such a sensor system may include a speedometer; anaccelerometer; one or more cameras, image sensors, laser sensors, RADARsensors, or infrared sensors directed to the road surface or topotential obstacles on the road (e.g., for autonomous or semi-autonomousdriving); a dedicated GPS receiver (not shown) disposed in the vehicle(e.g., in the interior, such as in the cabin, trunk, or enginecompartment, or on the exterior of the vehicle); a compass; etc. Thecontroller 127 may communicate with and rely on data from the sensorsystem to facilitate generating notifications for the user, controllingthe vehicle 103 in an autonomous or semi-autonomous fashion, etc.

3. The Vehicle Monitor Device 145

The vehicle monitor device 145 is a computer system that may include acontroller 147 (e.g., including a memory 147 and a processor 151), acommunication interface 153, and a set of sensors 161. While not shown,the vehicle monitor 145 may include UI components similar to the UIcomponents 115 and 135 in some embodiments.

The sensors 161 are configured to collect data to enable tracking of thebehavior of the vehicle 103 (e.g., braking, accelerating/decelerating,swerving, proximity to other vehicles, adherence to lane markers andother road markers, adherence to speed limits, etc.) or of the driverspecifically and distinct from observations of the vehicle (e.g., headpose or eye gaze direction indicating attention to the road, handplacement, etc.). The sensors 161 may include a speedometer; anaccelerometer; one or more cameras, image sensors, laser sensors, RADARsensors, or infrared sensors directed to the road surface, to potentialobstacles on the road, or to the driver (e.g., for autonomous orsemi-autonomous driving); a dedicated GPS receiver (not shown) disposedin the vehicle (e.g., in the interior, such as in the cabin, trunk, orengine compartment, or on the exterior of the vehicle); a compass; etc.

The memory 149 may include (i) a set of instructions 150 that, whenimplemented by the processor 151, cause the processor 151 to perform oneor more operations described herein regarding vehicle monitor 145, or(ii) data 152 (e.g., including input data on which the processor 151 mayoperate or output data generated by the processor 151).

In example operation, the controller 147 receives an activation command(e.g., via an input component or via the communication interface 153).The activation command may originate at any of the server 155, themobile device 105, or the OBC 125. In response to receiving the command,the controller 147 collects, via the sensors 161, data representingvehicle behavior or driver behavior. The controller 147 may transmit thedata to the server 155 for analysis (e.g., to identify the behavior anda corresponding risk profile adjustment if necessary). In someembodiments, the data may be transmitted to the OBC 125 or the mobiledevice 105 for analysis. In an embodiment, the controller 147 performsthe analysis.

The controller 147 may receive a deactivation command via an inputcomponent or via the communication interface 153. Again, this commandmay originate at any of the server 155, the mobile device 105, or theOBC 125. In response to receiving the deactivation command, thecontroller 147 stops collecting data via the sensors 161. In anembodiment, the controller 147 responds to the deactivation command bystopping the reporting of collected data for analysis, but continues tocollect data via the sensors 161. The data may be stored locally to thememory 149 in such an embodiment. If desired, a user may have controlover the collected data (e.g., he or she may have control over whetheror not the data is collected while the tracking service is off, orcontrol over whether or not the data is eventually reported foranalysis).

It will be understood that one or more components of the vehicle monitor145 (e.g., the controller 147) may be characterized as a vehicle monitorcircuit, and that any circuit providing the functionality describedherein as being provided by the vehicle monitor 145 may be referred toas a “vehicle monitor circuit.”

4. The Server 155

The server 155 is a computer system that may include a controller 147(e.g., including a memory 157 and a processor 161), a communicationinterface 163, and a set of user interface (UI) components 165 (e.g.,including an input component 167 and an output component 169). One ormore of the UI components 165 may be the same as, or similar to, thepreviously described UI components 115 and 135. The memory 159 mayinclude (i) a set of instructions 160 that, when implemented by theprocessor 161, cause the processor 161 to perform one or more operationsdescribed herein with respect to the server 155, or (ii) data 162 (e.g.,including input data on which the processor 161 may operate or outputdata generated by the processor 161).

In example operation, the server 155 coordinates the status(es) orcondition(s) of the devices or services in the in-vehicle computersystem 104 with the content delivery service provided via the CDS 175.For example, the server 155 may transmit messages to the CDS 175 to (i)cause the CDS 175 to activate content delivery when both the DND mode isactive and the vehicle tracking service is active and (ii) cause the CDS175 to deactivate content delivery to the system 104 when either the DNDmode or the vehicle tracking service goes inactive.

As an additional example, the server 155 may receive data collected bythe vehicle monitor 145. This data may represent behavior of the vehicle103 or of the driver of the vehicle. The server 155 may analyze the datato determine a level of riskiness associated with the driver based onthe analyzed behavior. The level may be an integer or float variablescaled from 0-100 (e.g., where 50 represents a median risk level). Asanother example, the level may have one of a predetermined set of valuessuch as “low risk,” “average risk,” “high risk” (or, e.g., acorresponding 1, 2, or 3 representing risk levels). Ultimately, aninsurance company may rely on the calculated level of riskiness todetermine a monthly premium to charge the driver.

5. The Content Delivery System 175

The content delivery system (CDS) 175 may be a host or server (ormultiple servers) including memory (not shown) storing media 176 or agame 178. The CDS 175 may be configured to deliver the media 176 or game178 to a requesting device (e.g., via streaming or via transmission forlocal download and replay by the requestor). The requesting device maybe any one or more of: the mobile device 105, the OBC 125, or thevehicle monitor 145.

In some instances, the CDS 175 streams the media 176 by transmittingon-demand (i.e., not necessitating long term storage at the system 104).In an embodiment, a copy of the media 176 may be stored at a memory ofthe system 104. The CDS 175 may transmit messages initiating or haltingthe display or output of the media 176 at the system 104.

The media 176 may be any suitable piece of audio or visual media. Forexample, the media 176 may be a set of songs, audiobooks, premium radio,etc. The game 178 may be any suitable game or gamified interfaceappropriate to display or otherwise provide to a user while the user isdriving.

C. Other Aspects of the Vehicle Computer System 100

Depending on the embodiment, the vehicle computer system 100 may havevarious configurations. For example, in an embodiment the vehiclecomputer system 100 may include only the in-vehicle system 104. In otherwords, the functionality of the vehicle computer system 100 may beprovided entirely by the in-vehicle system 104 in some embodiments. Assuch, the vehicle computer system 100 may be a “stand-alone” system thatdoes not require connection to an external network such as the network199 in some embodiments.

In an embodiment, the in-vehicle computer system 104 may include onlythe mobile device 105, only the OBC 125, or only the vehicle monitor145. In other words, the functionality of the vehicle computer system104 may be provided entirely by a single device in some embodiments.Indeed, each of the mobile device 105, the OBC 125, and the vehiclemonitor 145 may perform some or all of the processing associated withthe system 100 (e.g., also described with reference to FIG. 4) in someembodiments. For example, the mobile device 105 may include anapplication that collects data for the vehicle tracking service.

In some embodiments (and as shown in FIG. 1), the vehicle computersystem 100 may be a distributed system where the functionality of thevehicle computer system 100 is divided between the components 105-175.More generally speaking, although the vehicle computer system 100 isshown including one server 155, one mobile device 105, one OBC 125, onevehicle monitor 145, and one CDS 175, it will be understood that zero,one, or a plurality of each may be utilized depending on the embodiment.

In an embodiment, the processing performed by the server 155 or the CDS175 may be distributed among a plurality of servers in an arrangementreferred to as “cloud computing.” This configuration may provide severaladvantages, such as enabling near real-time uploads and downloads ofinformation as well as periodic uploads and downloads of information.This may provide for a thin-client embodiment of the mobile device 105,the OBC 125 or the vehicle monitor 145, as well as a primary backup ofsome or all of the data gathered by the mobile any of the devices 105,125, or 145.

Further, if desired, a database (e.g., implemented by the server 155)may store data related to the operation of the vehicle computer system100. Such data might include, for example, data collected by a mobiledevice 105, the OBC 125, or the vehicle monitor 145. Such data maypertain to the vehicle computer system 100 and may be uploaded to theserver 155 (e.g., images, sensor inputs, data analyzed according to themethods discussed below, or other kinds of data). The server 155 mayaccess data stored in such a database when executing various functionsand tasks associated with the operation of the vehicle computer system100. The data in such a database may be stored at one or more memorydevices included within, or otherwise communicatively connected to, theserver 155.

In an embodiment, any one or more of the devices 105, 125, and 145 maydrive any one or more of the displays 119, 139, and 159 if desired.Further, it will be appreciated that any one or more of the UIcomponents 115, 135, or 15 may be referred to as “UI devices.”

Below, the example vehicles 200 and the example displays 300 aredescribed in more detail before turning to the example method 400, whichmay be implemented by the system 100.

II. Example Vehicles 200 a-200 i

Turning to FIGS. 2A-2I, various embodiments of vehicle computer systems200 a-200 i are shown, each of which may be similar to the vehiclecomputer system 100 shown in FIG. 1A and each of which may provide thesame or similar functionality to that described regarding the system100. The vehicle computer systems 200 a-200 i include vehicles 205 a-205i, each of which may include the in-vehicle computer system 104 shown inFIG. 1 or some version thereof.

Specifically, the system 104 may be implemented utilizing any of thefollowing vehicles: (a) an automobile 205 a as shown in FIG. 2A; (b) amotorcycle 205 b as shown in FIG. 2B; (c) a watercraft (e.g., yacht orcommercial ship) 205 c as shown in FIG. 2C; (d) a commercial automobile(e.g., a semi-truck) 205 d as shown in FIG. 2D; (e) a personalwatercraft (e.g., a jet-ski) 205 e as shown in FIG. 2E; (f) an aircraft205 f as shown in FIG. 2F; (g) a recreational vehicle (e.g., a camper)205 g as shown in FIG. 2G; (h) a train 205 h as shown in FIG. 2H; or (i)a four-wheeler 200 i as shown in FIG. 2I.

III. Example Displays 300

FIG. 3 illustrates a set of example display devices 300 according tovarious embodiments, including example displays 300 a-300 f. Each of thedisplay devices 300 may be part of the system 100 shown in FIG. 1, andeach may be utilized in place of or in addition to any one or more ofthe display devices shown in FIG. 1. Each display device 300 may besimilar in nature to any of the display devices 119, 139, or 159 shownin FIG. 1, capable of performing similar functions and interfacing withthe same or similar systems; and each of the devices 105, 125, and 145may provide output via any of the displays 300 a-300 f, in addition toor in place of the displays 119, 139, or 159, if desired.

In an embodiment, the display devices 300 may display the media data 176or the game data 178 shown in FIG. 1. More generally, each of thedisplay devices 300 may present visual information based on video dataor image data received from any of the devices 105, 125, or 145 shown inFIG. 1.

As shown, the display device 300 a is a screen of a mobile phone 311(e.g., representing an example of the mobile device 105). The displaydevice 300 b is an in-dash display for a vehicle 313 (e.g., representingan example of the vehicle 103). The display device 300 c is a projectorfor a projector device 315 (e.g., representing an example of the mobiledevice 105). The display device 300 d is a heads-up display (HUD) for avehicle (e.g., the vehicle 103) projected onto a windshield 317. Thedisplay device 300 e is a screen for a tablet 319 (e.g., representing anexample of the mobile device 105). The display device 300F is a screenfor a laptop 321 (e.g., representing an example of the mobile device105).

IV. An Example Method 400 for Incentivizing Vehicle Tracking and SafeVehicle Operation

FIG. 4 illustrates an example method 400 for incentivizing vehicletracking and safe vehicle operation according to an embodiment. Themethod 400 may be implemented, in whole or in part, by the system 100shown in FIG. 1. The method 100 may be saved to a memory (e.g., any oneor more of the memories 109, 129, 149, or 159) as one or moreinstructions or routines.

At a high level, in an example implementation of the method 400, thesystem 100 may perform any one or more of the following functions: (a)detect a user (block 401); (ii) detect a first condition indicating adrive tracking service is active (e.g., wherein vehicle operation istracked by the vehicle monitor 145) (block 404); (iii) detect a secondcondition indicating the mobile device 105 is in DND mode (block 412);and (iv) automatically synchronize a content delivery service (e.g.,provided by the CDS 175 shown in FIG. 1) to a device within the vehicle103 (block 425).

A. Detecting a Driver's Presence (Block 401)

The system 100 may detect a user (block 401). In an embodiment, thesystem 100 automatically detects the user. For example, the system 100may detect the mobile device 105 automatically connecting (e.g., viaBluetooth or wifi) to the OBC 125. As another example, the OBC 125 ofthe vehicle 103 may include a proximity sensors (e.g., utilizing: photosensors that emit and detect reflected visible or non-visible light;RADAR; a camera: laser sensors; infrared sensors detecting the user'sbody heat as she approaches the vehicle; etc.). As yet another example,the system 100 may rely on a position sensor (e.g., GPS) of the mobiledevice 105 to determine the user is in or near the vehicle 103. In someinstances, the mobile device 105 or the OBC 125 may, when configured todetect the user's presence as described herein, may be referred to as“user detection circuits” or as including “user detection circuits.”

In an embodiment, the system 100 detects the user based on user input.As an example, the system 100 may detect the vehicle 103 starting (e.g.,the ignition being used, the engine starting, etc.). The system 100 maydetect a user activating the vehicle monitor 145 (e.g., via a button ona housing of the vehicle monitor 145 or via a software button displayedon one of the displays 119, 139, 159).

B. Detecting an Active Drive Tracking Service (Block 404)

The system 100 may detect a status of a drive tracking service (e.g.,indicating whether or not the vehicle monitor 145 is tracking vehicleoperation) (block 404). A variable representing the condition may bestored to a memory of the system 100, and may be adjusted by acontroller of the system 100 in response to detecting a change in thestatus of the drive tracking service. The block 404 may include a set ofblocks 405 and 410.

In example operation, a user, the server 155, or the OBC 125 mayactivate a tracking service implemented via the vehicle monitor 145(block 405). In an embodiment, the tracking service is automaticallyactivated in response to a trigger. The trigger may be: a detection ofthe vehicle 103 starting; a detection of the mobile device 105 or of auser in or near the vehicle; a detection of a communication connection(e.g., Bluetooth) between the mobile device 105 and another devicewithin the system 104; a detection of a preconfigured setting indicatingthe service should start automatically; or some combination thereof.When the tracking service is active, the vehicle monitor 145 maytransmit data to the server 155 regarding behavior of the vehicle 103.For example, the data may indicate miles driven, a particular pathdriven, acceleration/deceleration information, braking information,swerving information, distance from nearest car information, timestamps, information regarding the driver's eye gaze (e.g., indicatinghow often the driver is looking at the road vs somewhere else),information regarding the driver's hand placement on the steering wheel,etc. The server 155 may analyze the data, and the results of theanalysis may be utilized to assign a level of riskiness to the driver,which may be used to determine an insurance rate for the driver. In someembodiments, the tracking service is implemented by the mobile device105 or the OBC 125 or by some combination of the devices 105, 125, and145.

The system 100 may detect that the tracking service has been activatedby monitoring the vehicle monitor 145 (block 420). For example, thevehicle monitor 145 may transmit a signal to the mobile device 105, theOBC 125, or the server 155 carrying a message indicating the trackingservice has been activated.

C. Detecting an Active DND Mode (Block 412)

The system 100 may detect a status of a DND mode of the mobile device105 (block 412). The block 412 may include blocks 415 and 420.

In example operation, the mobile device 105 may initiate DND mode (block415). This initiation may be automatic (e.g., triggered by a triggerother than a user) or manual (e.g., triggered by a user). For example,automatic initiation may occur in response to detecting the trackingservice is active. As an example, the monitor 145 may transmit a messageto the mobile device 105 directly (e.g., via a PAN such as Bluetooth orNFC or via wifi) or indirectly (e.g., via the OBC 125 or the server155), wherein the message indicates the tracking service is active. Asanother example, the DND mode may be automatically triggered bydetecting that the vehicle 103 has started or is moving. For example,utilizing internal sensors, the mobile device 105 may detect and analyzea speed and direction to determine the mobile device is moving in avehicle, and may trigger the DND mode. As another example, the OBC 125may communicate with the mobile device 105 directly or indirectly tonotify that mobile device 105 that the vehicle 103 has started or ismoving, and the mobile device 105 may respond to the notification byautomatically entering DND mode. In some instances, any suitablecombination of these described triggers may be used or required toautomatically trigger DND mode. In some instances, a user manuallyplaces the mobile device 105 in DND mode (e.g., by interacting with abutton displayed via a GUI of the mobile device 105.

The system 100 may detect that the DND mode is active by tracking ormonitoring the mobile device 105 (block 420). For example, the server155, the OBC 125, or the vehicle monitor 145 may periodically transmit amessage to the mobile device 105, requesting a verification message fromthe mobile device 105 that verifies the status of mobile device 105 withrespect to the DND mode. In an embodiment, the mobile device 105 reportsstate changes to and from DND mode (e.g., to the server 155 or the OBC125). According, the server 155 may receive a notification of each statechange in and out of DND mode, enabling the server 155 to track thestatus of the DND mode and to coordinate content delivery accordingly.

D. Automatically Sync the Media Service to Drive Tracking Service andDND Mode (Block 425)

The system 100 may automatically synchronize a content delivery service(e.g., provided by the CDS 175) to a device within the vehicle 103(block 425).

In example operation, the system 100 may: (i) respond to receiving ordetecting the status of the drive tracking service by determiningwhether or not the status indicates the drive tracking service is active(block 430); and (ii) respond to receiving or detecting the status ofthe DND mode of the mobile device 105 by determining whether or not thestatus indicates the DND mode is active (block 440).

As shown, if either the driver tracking service is inactive or the DNDmode is inactive, the system 105 deactivates the media service from theCDS 175 or maintains a current state if the media service is alreadyinactive (block 435). Deactivating the media service may include any oneof the devices 105, 125, or 145 detecting that either the DND mode orthe tracking service is inactive, and transmitting a message to theserver 155 to indicate that the media service is no longer authorized.In an embodiment, deactivating the media service may include any one ofthe devices 105, 125, or 145 detecting that either the DND mode or thetracking service is inactive, and transmitting a message to the server155 carrying the relevant status. The server 155 may then respond toreceiving the message by sending a message to the CDS 175 indicatingthat the media service is not authorized, and the CDS 175 may respond bystopping the media service. After block 435, the system 100 returns tothe beginning of step 425 to maintain a synchronized state between themedia delivery service and the drive tracking service and the DND mode.

If both the drive tracking service is active and the DND mode is active,the system 100 activates the media service from the CDS 175 or maintainsa current state if the media service is already active (block 445).Activating the media service may include any one of the devices 105,125, or 145 detecting that both the DND mode and the tracking service isactive, and transmitting a message to the server 155 to indicate thatthe media service is authorized. In an embodiment, activating the mediaservice may include any one of the devices 105, 125, or 145 detectingthe status of the DND mode and the drive tracking service, andtransmitting a message to the server 155 carrying the statuses. Theserver 155 may then respond to receiving the message by sending amessage to the CDS 175 indicating that the media service is authorized,and the CDS 175 may respond by initiating the media service. After block445, the system 100 returns to the beginning of step 425 to maintain asynchronized state between the media delivery service and the drivetracking service and the DND mode.

The media service may be any suitable audio streaming or deliveryservice, such as a music streaming service, a podcast streaming service,etc. In some embodiments, the media service plays audio local to theenvironment 104 (e.g., audio stored locally to the mobile device 105).

V. Additional Considerations

With the foregoing, an insurance customer may opt-in to a rewards,insurance discount, or other type of program. After the insurancecustomer provides their affirmative consent, an insurance providerremote server may collect data from the customer's mobile device, smarthome controller, or other smart devices—such as with the customer'spermission or affirmative consent. The data collected may be related tovehicle operation or insured assets before (or after) aninsurance-related event, including those events discussed elsewhereherein. In return, risk averse insureds may receive discounts orinsurance cost savings related to vehicle, life or other types ofinsurance from the insurance provider.

When implemented in software, any of the applications, services, andengines described herein may be stored in any tangible, non-transitorycomputer readable memory such as on a magnetic disk, a laser disk, solidstate memory device, molecular memory storage device, or other storagemedium, in a RAM or ROM of a computer or processor, etc. Although theexample systems disclosed herein are disclosed as including, among othercomponents, software or firmware executed on hardware, it should benoted that such systems are merely illustrative and should not beconsidered as limiting. For example, it is contemplated that any or allof these hardware, software, and firmware components could be embodiedexclusively in hardware, exclusively in software, or in any combinationof hardware and software. Accordingly, while the example systemsdescribed herein are described as being implemented in software executedon a processor of one or more computer devices, persons of ordinaryskill in the art will readily appreciate that the examples provided arenot the only way to implement such systems.

Referencing the method 400 specifically, the described functions may beimplemented, in whole or in part, by the devices, circuits, or routinesof the system 100 shown in FIG. 1. The described method may be embodiedby a set of circuits that are permanently or semi-permanently configured(e.g., an ASIC or FPGA) to perform logical functions of the respectivemethod or that are at least temporarily configured (e.g., one or moreprocessors and a set instructions or routines, representing the logicalfunctions, saved to a memory) to perform the logical functions of therespective method.

While the present invention has been described with reference tospecific examples, which are intended to be illustrative only and not tobe limiting of the invention, it will be apparent to those of ordinaryskill in the art that changes, certain additions or deletions may bemade to the disclosed embodiments without departing from the spirit andscope of the invention. Further, although the forgoing text sets forth adetailed description of numerous different embodiments, it should beunderstood that the scope of the patent is defined by the words of theclaims set forth at the end of this patent and their equivalents. Thedetailed description is to be construed as exemplary only and does notdescribe every possible embodiment because describing every possibleembodiment would be impractical, if not impossible.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently in certain embodiments.

As used herein, any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

Further, the phrase “wherein the system includes at least one of X, Y,or Z” means the system includes an X, a Y, a Z, or some combinationthereof. Similarly, the phrase “wherein the component is configured forX, Y, or Z” means that the component is configured for X, configured forY, configured for Z, or configured for some combination of X, Y, and Z.

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This description, and theclaims that follow, should be read to include one or at least one. Thesingular also includes the plural unless it is obvious that it is meantotherwise.

In various embodiments, hardware systems described herein may beimplemented mechanically or electronically. For example, a hardwaresystem may comprise dedicated circuitry or logic that is permanentlyconfigured (e.g., as a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an application-specific integratedcircuit (ASIC) to perform certain operations). A hardware system mayalso comprise programmable logic or circuitry (e.g., as encompassedwithin a general-purpose processor or other programmable processor) thatis temporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware systemmechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Further, the patent claims at the end of this document are not intendedto be construed under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being explicitly recited in the claim(s). Atleast some aspects of the systems and methods described herein aredirected to an improvement to computer functionality, and improve thefunctioning of conventional computers.

VI. General Terms and Phrases

Throughout this specification, some of the following terms and phrasesare used.

Cloud/Cloud Computing. The phrase “cloud computing” generally refers toa variety of concepts involving a large number of computers connectedthrough a network (e.g., the Internet). In common usage, “the cloud” isoften a metaphor for the Internet. “In the cloud” often refers tosoftware, platforms, and infrastructure sold “as a service” (i.e.,remotely through the Internet). The supplier of these services generallyutilizes servers hosting products and services from a remote location,enabling individual users to access these products and services via theservers while requiring the users to install little if any software ontheir end-user devices. Example models of cloud computing services maybe referred to as “software as a service,” “platform as a service,” and“infrastructure as a service.” Cloud services may be offered in apublic, private, or hybrid networks and may be implemented on hostsprovided by third-party cloud vendors.

Communication Interface. Some of the described devices or systemsinclude a “communication interface” (sometimes referred to as a “networkinterface”). For example, each of the systems 105, 125, 145, 155, and175 may include a communication interface. Each of the describedcommunication interfaces enables the system of which it is a party to(i) send information or data to other systems or components or (ii)receive information or data from other systems or components. Acommunication interface configured to enable a system to couple to aperipheral device (e.g., a keyboard, a monitor, an external hard drive,etc.) may be referred to as a “peripheral interface” or “I/O interface”(see “I/O interface”). In some instances, one or more of the describedcommunication interfaces may be utilized to establish a directconnection to another system. In some instances, one or more of thedescribed communication interfaces enable the system(s) of which theyare a part to connect via a link to a network (e.g., a personal areanetwork (PAN), a local area network (LAN), or a wide area network(WAN)).

If desired, the described communication interfaces may include (i)circuitry that enables connection to a wired link that carrieselectrical or optical signals to another device (e.g., via a coax cableor fiber optic cable) and to communicate with that other device, or (ii)circuitry that enables wireless communication (e.g., short-range orlong-range communication) via electromagnetic signals, such as radiofrequency (RF) signals. Further, in some instances a describedcommunication interface may refer to multiple interfaces forcommunicating with components or systems external to a system. Forexample, in some instances, a described communication interface mayrefer to a set of communication interfaces including: one or more wiredcommunication interfaces, one or more wireless communication interfaces,and one or more I/O or peripheral interfaces. The describedcommunication interfaces and systems may conform to any one or moresuitable communications protocols, standards, or technologies, such asthose described herein

Communication Protocols. In this description, communication protocols,standards, and technologies may be referred to generically as“communication protocols.” Example communication protocols, standards,or technologies that may be utilized by the described systems includethose that facilitate communication via nanoscale networks, near-fieldnetworks, personal area networks (“PANs”), local area networks (“LANs”),backbone networks, metropolitan area networks (“MANs”), wide areanetworks (“WANs”), Internet area networks (“IANs”), or the Internet.

Example near-field network protocols and standards include typicalradio-frequency identification (“RFID”) standards or protocols andnear-field communication (“NFC”) protocols or standards. Example PANprotocols and standards include 6LoWPAN, Bluetooth (i.e., a wirelessstandard for exchanging data between two devices using radio waves inthe range of approximately 2.4 to 2.485 GHz), IEEE 802.15.4-2006,ZigBee, the Thread protocol, ultra-wideband (“UWB”), universal serialbus (“USB”) and wireless USB, and ANT+. Example LAN protocols andstandards include the 802.11 protocol and other high frequencyprotocols/systems for wireless communication in bands found in a rangeof approximately 1 GHz-60 GHz (e.g., including the 900 MHz, 2.4 GHz, 3.6GHz, 5 GHz, or 60 GHz bands), as well as standards for suitable cablingsuch as coaxial and fiber-optic cabling. Example technologies used tofacilitate wireless WANs includes those used for LANs, as well as 2G(e.g., GPRS and EDGE), 3G (e.g., UMTS and CDMA2000), 4G (e.g., LTE andWiMax), and 5G (e.g., IMT-2020) technologies. Note, the Internet may beconsidered a WAN.

Other communication protocols and standards that may be utilized includeBitTorrent, Bluetooth Bootstrap Protocol (“BOOTP”), Domain Name System(“DNS”), Dynamic Host Configuration Protocol (“DHCP”), Ethernet, filetransfer protocol (“FTP”), hypertext transfer protocol (“HTTP”),infrared communication standards (e.g., IrDA or IrSimple), transmissioncontrol protocol/internet protocol (“TCP/IP”) (e.g., any of theprotocols used in each of the TCP/IP layers), real-time transportprotocol (“RTP”), real-time streaming protocol (“RTSP”), Simple MailTransfer Protocol (“SMTP”), Simple Network Management Protocol (“SNMP”),Simple Network Time Protocol (“SNTP”), secure shell protocol (“SSH”),and any other communications protocol or standard, or any combinationthereof.

Communication Link. Unless otherwise stated, a “communication link” or a“link” is a pathway or medium connecting two or more nodes. A link maybe a physical link or a logical link. A physical link is the interfaceor medium(s) over which information is transferred, and may be wired orwireless in nature. Example physicals links include (i) wired links suchas cables with a conductor for transmission of electrical energy or afiber optic connections for transmission of light and (ii) wirelesslinks such as wireless electromagnetic signals that carry informationvia changes made to one or more properties of electromagnetic waves.

As noted, a wireless link may be a wireless electromagnetic signal thatcarries information via changes made to one or more properties of anelectromagnetic wave(s). A wireless electromagnetic signal may be amicrowave or radio wave and may be referred to as a radio frequency or“RF” signal. Unless otherwise stated, described RF signals mayoscillated at a frequency within any one or more bands found in thespectrum of roughly 30 kHz to 3,000 GHz (e.g., an 802.11 signal in the2.4 GHz band). Example RF bands include the low frequency (“LF”) band at30-300 kHz, the medium frequency (“MF”) band at 300-3,000 kHz, the highfrequency (“HF”) band at 3-30 MHz, the very high frequency (“VHF”) bandat 30-300 MHz, the ultra-high frequency (“UHF”) band at 300-3,000 MHz,the super high frequency (“SHF”) band at 3-30 GHz, the extremely highfrequency (“SHF”) band at 30-300 GHz, and the tremendously highfrequency (“THF”) band at 300-3,000 GHz.

A logical link between two or more nodes represents an abstraction ofthe underlying physical links or intermediary nodes connecting the twoor more nodes. For example, two or more nodes may be logically coupledvia a logical link. The logical link may be established via anycombination of physical links and intermediary nodes (e.g., routers,switches, or other networking equipment).

A link is sometimes referred to as a “communication channel.” In awireless communication system, the term “communication channel” (or just“channel”) generally refers to a particular frequency or frequency band.A carrier signal (or carrier wave) may be transmitted at the particularfrequency or within the particular frequency band of the channel. Insome instances, multiple signals may be transmitted over a singleband/channel. For example, signals may sometimes be simultaneouslytransmitted over a single band/channel via different sub-bands orsub-channels. As another example, signals may sometimes be transmittedvia the same band by allocating time slots over which respectivetransmitters and receivers use the band in question.

Computer. Generally speaking, a computer or computing device is aprogrammable machine having two principal characteristics. Namely, itresponds to a set of instructions in a well-defined manner and canexecute a prerecorded list of instructions (e.g., a program or routine).A computer according to the present disclosure is a device with aprocessor and a memory. For purposes of this disclosure, examples of acomputer include a server host, a personal computer, (e.g., desktopcomputer, laptop computer, netbook), a mobile communications device(such as a mobile “smart” phone), and devices providing functionalitythrough internal components or connection to an external computer,server, or global communications network (such as the Internet) to takedirection from or engage in processes which are then delivered to othersystem components.

Database. Generally speaking, a “database” is an organized collection ofdata, generally stored and accessed electronically from a computersystem. Generally, any suitable datastore may be referred to as a“database.” This disclosure may describe one or more databases forstoring information relating to aspects of the disclosure. Theinformation stored on a database can, for example, be related to aprivate subscriber, a content provider, a host, a security provider,etc. A server (which may or may not be hosted on the same computer asthe database) may act as an intermediary between the database and aclient by providing data from the database to the client or enabling theclient to write data to the database. One of ordinary skill in the artappreciates any reference to “a database” my refer to multipledatabases, each of which may be linked to one another.

Display Device. Generally speaking, the terms “display device” or“display” refer to an electronic visual display device that providesvisual output in the form of images, text, or video. The describeddisplay devices (e.g., 119, 139, 159, 169, 300) may be any display,screen, monitor, or projector suitable for displaying visual output(e.g., images or video output). Example displays include LED screens,LCD screens, CRT screens, projectors, heads up displays, smart watchdisplays, headset displays (e.g., VR goggles), etc.

Graphic User Interface (GUI). See “User Interface.”

Memory and Computer-Readable Media. Generally speaking, as used hereinthe phrase “memory” or “memory device” refers to a system or deviceincluding computer-readable media or medium (“CRM”). “CRM” refers to amedium or media accessible by the relevant computing system for placing,keeping, or retrieving information (e.g., data, computer-readableinstructions, program modules, applications, routines, etc). Note, “CRM”refers to media that is non-transitory in nature, and does not refer todisembodied transitory signals, such as radio waves.

The CRM may be implemented in any technology, device, or group ofdevices included in the relevant computing system or in communicationwith the relevant computing system. The CRM may include volatile ornonvolatile media, and removable or non-removable media. The CRM mayinclude, but is not limited to, RAM, ROM, EEPROM, flash memory, or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store information and which can be accessed by the computingsystem. The CRM may be communicatively coupled to a system bus, enablingcommunication between the CRM and other systems or components coupled tothe system bus. In some implementations the CRM may be coupled to thesystem bus via a memory interface (e.g., a memory controller). A memoryinterface is circuitry that manages the flow of data between the CRM andthe system bus.

Message. When used in the context of communication networks, the term“message” refers to a unit of communication, represented by a set ofdata, transmitted or received by a node (e.g., via a link). The set ofdata representing the message may include a payload (i.e., the contentintended to be delivered) and protocol overhead. The overhead mayinclude routing information and metadata pertaining to the protocol orpayload (e.g., identifying the protocol for the message, the intendedrecipient node, the originating node, the size of the message orpayload, data integrity information for checking the integrity of themessage, etc.). In some instances, a packet or sequence of packets maybe thought of as a message.

Network. As used herein and unless otherwise specified, when used in thecontext of system(s) or device(s) that communicate information or data,the term “network” refers to a collection of nodes (e.g., devices orsystems capable of sending, receiving or forwarding information) andlinks which are connected to enable telecommunication between the nodes.

Each of the described networks (e.g., the networks 101 and 199) mayinclude dedicated routers, switches, or hubs responsible for forwardingor directing traffic between nodes, and, optionally, dedicated devicesresponsible for configuring and managing the network. Some or all of thenodes of the described networks may be adapted to function as routers inorder to direct traffic sent between other network devices. Nodes of thedescribed networks may be inter-connected in a wired or wireless manner,and may have different routing and transfer capabilities. For example,dedicated routers may be capable of high-volume transmissions while somenodes may be capable of sending and receiving relatively little trafficover the same period of time. Additionally, the connections betweennodes on the described networks may have different throughputcapabilities and different attenuation characteristics. A fiberopticcable, for example, may be capable of providing a bandwidth severalorders of magnitude higher than a wireless link because of thedifference in the inherent physical limitations of the medium. Each ofthe described networks may include networks or sub-networks, such as alocal area network (LAN) or a wide area network (WAN).

Node. Generally speaking, the term “node” refers to a connection point,redistribution point, or a communication endpoint. A node may be anydevice or system (e.g., a computer system) capable of sending, receivingor forwarding information. For example, end-devices or end-systems thatoriginate or ultimately receive a message are nodes. Intermediarydevices that receive and forward the message (e.g., between twoend-devices) are also generally considered to be “nodes.”

Processor. The various operations of example methods described hereinmay be performed, at least partially, by one or more processors.Generally speaking, the terms “processor” and “microprocessor” are usedinterchangeably, each referring to a computer processor configured tofetch and execute instructions stored to memory. By executing theseinstructions, the processor(s) can carry out various operations orfunctions defined by the instructions. The processor(s) may betemporarily configured (e.g., by instructions or software) orpermanently configured to perform the relevant operations or functions(e.g., a processor for an Application Specific Integrated Circuit, orASIC), depending on the particular embodiment. A processor may be partof a chipset, which may also include, for example, a memory controlleror an I/O controller. A chip set is a collection of electroniccomponents in an integrated circuit that is typically configured toprovide I/O and memory management functions as well as a plurality ofgeneral purpose or special purpose registers, timers, etc. Generallyspeaking, one or more of the described processors may be communicativelycoupled to other components (such as memory devices and I/O devices) viaa system bus.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the processor or processors may be located in a single location (e.g.,within a home environment, an office environment or as a server farm),while in other embodiments the processors may be distributed across anumber of locations.

Words such as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

Routine. Unless otherwise noted, a “routine,” “module,” or “application”described in this disclosure refers to a set of computer-readableinstructions that may be stored on a CRM. Generally, a CRM storescomputer-readable code (“code”) representing or corresponding to theinstructions, and the code is adapted to be executed by a processor tofacilitate the functions described as being represented by or associatedwith the routine or application. Each routine or application may beimplemented via a stand-alone executable file, a suite or bundle ofexecutable files, one or more non-executable files utilized by anexecutable file or program, or some combination thereof. In someinstances, unless otherwise stated, one or more of the describedroutines may be hard-coded into one or more EPROMs, EEPROMs, applicationspecific integrated circuits (ASICs), field programmable gate arrays(FPGAs), or any other hardware or firmware elements.

Further, unless otherwise stated, each routine or application may beembodied as: (i) a stand-alone software program, (ii) a module orsub-module of a software program, (iii) a routine or sub-routine of asoftware program, or (iv) a resource invoked or accessed by a softwareprogram via a “call” to thereby cause the system to implement the taskor function associated with the resource. The call may be (i) a“function call” that is invoked to cause execution of a resource (e.g.,set of instructions) stored at a library accessible by the softwareprogram; (ii) a “system call” that is invoked to cause execution of asystem resource (e.g., often running in privileged kernel space and onlyexecutable only by the operating system); (iii) a “remote call” that isinvoked to cause a logical or physical entity with a different addressspace to execute a resource; or (iv) some combination thereof. As anexample, a routine executed by a processor of a device may invoke a“remote call” to cause execution of a resource at (i) a second device(e.g., a server host, an end-user device, a networking device, aperipheral device in communication with the device, or some otherphysical device); (ii) a virtual-machine on the same or differentdevice; (iii) a processor (e.g., CPU or GPU) that is different from theoriginal processor and that may be internal or external to the deviceexecuting the routine; or (iv) some combination thereof.

Each routine may be represented by code implemented in any desiredlanguage, such as source code (e.g., interpretable for execution orcompilable into a lower level code), object code, bytecode, machinecode, microcode, or the like. The code may be written in any suitableprogramming or scripting language (e.g., C, C++, Java, Actionscript,Objective-C, Javascript, CSS, Python, XML, Swift, Ruby, Elixir, Rust,Scala, or others).

Server. Generally speaking, a server is a program or set of routinesthat manages network resources or services to provide functionality forother programs or devices called “clients.” Servers are typically hostedby a host computer, and this host computer may itself be referred to asa “server.” Example servers include database servers, file servers, mailservers, print servers, web servers, game servers, and applicationservers. Servers may be dedicated (e.g., wherein the software andhardware are used exclusively or nearly exclusively for serverfunctions) or virtual (e.g., wherein the server is hosted by a virtualmachine on a physical machine or wherein the server shares hardware orsoftware resources of a single machine with another operating system).

User Interface (UI). Generally speaking, a user interface refers to thecomponents of a computer system by which a user and the computer systeminteract. The UI components may be hardware, software, or somecombination thereof, and may include UI input components, UI outputcomponents, or some combination thereof. In some embodiments, any one ormore of the UI components 115, 135, or 165 shown in FIG. 1 may includeany one or more of the example UI components listed below.

Example UI output components include: (i) visual output components suchas lights (e.g., LEDs) and electronic displays (e.g., LCD, LED, CRT,plasma, projection displays, heads-up displays, etc.), (ii) audio outputcomponents such as speakers, and (iii) motion generating components suchas motors that provide haptic feedback.

Example UI input components include: (i) mechanical or electricalcomponents for detecting physical or touch input, such as hardwareactuators (e.g., those used for a keyboard, a mouse, “hard” buttonsfound on a tablet or phone, etc.) or electrical sensors (e.g., resistiveor capacitive touch sensors); (ii) audio sensors (e.g., microphones) fordetecting audio input, such as voice commands; (iii) image sensors fordetecting image or video input, such as those found in a camera (e.g.,enabling facial recognition input or gesture input without requiring theuser to touch the device); and (iv) motion sensors (e.g.,accelerometers, gyroscopes, etc.) for detecting motion of the computersystem itself (e.g., enabling a user to provide input by rotating orotherwise moving the computer system).

Some systems (e.g., the mobile device 105, the OBC 125, etc.) provide agraphical user interface (GUI) by way of a UI output component such asan electronic display (e.g., any of the displays 119, 139, 169, or 300).Generally speaking, a GUI is generated via a routine and enables a userto interact with indicators and other graphic elements displayed on atthe electronic display. Generally speaking, the graphic elements of aGUI may be output elements (i.e., conveying some sort of information tothe user), control elements (i.e., being user “interactable” to causethe execution of an action by the system), or both (e.g., an icon mayinclude an image representing a browser and may be interacted with tolaunch the browser).

Example GUI control elements include buttons (e.g., radio buttons, checkboxes, etc.), sliders, list boxes, spinner elements, drop-down lists,menus, menu bars, toolbars, interactive icons, text boxes, windows thatcan be moved or minimized and maximized, etc.

1-20. (canceled)
 21. A system for a media service at a vehicle duringdriving sessions, the system comprising: a vehicle monitor devicedisposed within the vehicle and configured to implement at least a partof a drive tracking service, the vehicle monitor device configured tocollect data representing vehicle operation; and a mobile deviceconfigured to: track a first status of the drive tracking service; tracka second status of the mobile device; automatically synchronize a mediaservice with the first status of the vehicle monitor device and thesecond status of the mobile device, including: transmit a message to aserver to activate the media service to provide media content in amanner receivable by a user in the vehicle when each condition of a setof conditions is true, wherein the set of conditions includes: (1) afirst condition that is true when the first status indicates the drivetracking service is active and that is otherwise false, and (2) a secondcondition that is true when the second status indicates the mobiledevice is in a do-not-disturb (“DND”) mode and that is otherwise false;and transmit a message to the server to deactivate the media service tostop providing the media content when any one condition of the set ofconditions is not true.
 22. The system of claim 21, wherein the vehiclemonitor device comprises an image sensor that is directed to the cockpitand configured to capture images of a head of a driver, wherein thedrive tracking service is configured to estimate a head pose or eye gazeof the driver based on the captured images.
 23. The system of claim 21,wherein the vehicle monitor device comprises a plurality of sensors fortracking driving behaviors of the vehicle.
 24. The system of claim 21,wherein the drive tracking service is configured to be active inresponse to a trigger event.
 25. The system of claim 21, wherein themobile device is configured to transmit a message authorizing the mediaservice based on the first and second statuses.
 26. The system of claim21, wherein the mobile device is configured to transmit a messagecarrying the first status and the second status, and wherein the serveris configured to activate or deactivate the media service based on thefirst and second statuses.
 27. The system of claim 21, wherein the DNDmode is a state of operation of the mobile device in which audionotifications are deactivated or muted.
 28. A method for a media serviceat a vehicle during driving sessions, the method comprising: tracking afirst status of a drive tracking service, the drive tracking serviceconfigured to track vehicle operation of the vehicle; tracking a secondstatus of a mobile device associated with a user; automaticallysynchronizing a media service with the first status of the drivetracking service and the second status of the mobile device by:automatically activating the media service to provide media content in amanner receivable by the user when each condition of a set of conditionsis true, wherein the set of conditions includes: (a) a first conditionthat is true when the first status indicates the drive tracking serviceis active and that is otherwise false, and (b) a second condition thatis true when the second status indicates the mobile device is in ado-not-disturb (“DND”) mode and that is otherwise false; automaticallydeactivating the media service to stop providing the media content whenany one of the set of conditions is not true.
 29. The method of claim28, wherein at least a part of the drive tracking service is implementedby a vehicle monitor device, wherein the vehicle monitor device includesan image sensor configured to capture images of a head of a driver toenable estimation of either a head pose or an eye gaze based on ananalysis of the images.
 30. The method of claim 29, wherein the vehiclemonitor device includes a plurality of sensors for tracking drivingbehaviors of the vehicle.
 31. The method of claim 28, wherein the drivetracking service is configured to be active in response to a triggerevent.
 32. The method of claim 28, further comprising: transmitting,based on the first and second statuses, a message to a server thatprovides or revokes an authorization for the media service.
 33. Themethod of claim 28, further comprising: transmitting, to a server, amessage including the first and second statuses, wherein the server isconfigured to authorize or unauthorize the media service based on thefirst and second statuses.
 34. The method of claim 28, wherein the DNDmode is a state of operation of the mobile device in which data andcellular interfaces of the mobile device are deactivated.
 35. A systemfor a media service at a vehicle during driving sessions, the systemcomprising: a mobile device; a server communicatively coupled to themobile device, the server configured to: detect a presence of the mobiledevice within a vehicle; track a first status of a drive trackingservice, the drive tracking service implemented by the mobile device orby a second one or more devices disposed within the vehicle, track asecond status of the mobile device; and automatically synchronize amedia service with the first status of the drive tracking service andthe second status of the mobile device, including: activate the mediaservice to provide media content via the mobile device or via the secondone or more devices disposed within the vehicle such that the mediacontent is receivable by the user when a set of conditions are true,wherein the set of conditions includes: (1) a first condition that istrue when the first status indicates the drive tracking service isactive and that is otherwise false, and (2) a second condition that istrue when the second status indicates the mobile device is in ado-not-disturb (“DND”) mode and that is otherwise false; and deactivatethe media service to stop providing the media content when any one ofthe set of conditions is false.
 36. The system of claim 35, wherein theserver is configured to detect the presence of the mobile device withinthe vehicle by receiving a message from the mobile device indicating atleast one of: (i) a request to activate the drive tracking service; and(ii) a verification that the drive tracking service has been activated.37. The system of claim 35, wherein the server is configured to trackthe first and second statuses by receiving messages from at least one ofthe mobile device and the one or more second devices.
 38. The system ofclaim 35, wherein the server is configured to track the first and secondstatuses by receiving messages from the one or more second devices. 39.The system of claim 35, wherein the server is configured toautomatically activate the media service, based on the set ofconditions, by transmitting a message to a content delivery system tocause the content delivery system to transmit the media content to themobile device or to the second one or more devices.
 40. The system ofclaim 35, wherein the drive tracking service is configured to be activein response to a trigger event.